-
Notifications
You must be signed in to change notification settings - Fork 9.7k
Fix framework identity interceptor #44518
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Community GuidelinesThis comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀 Voting for Prioritization
Pull Request Authors
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀
% make t K=ec2 T=TestAccVPCSecurityGroupIngressRule_Identity
make: Verifying source code with gofmt...
==> Checking that code complies with gofmt requirements...
make: Running acceptance tests on branch: 🌿 b-identity-for-framework 🌿...
TF_ACC=1 go1.24.6 test ./internal/service/ec2/... -v -count 1 -parallel 20 -run='TestAccVPCSecurityGroupIngressRule_Identity' -timeout 360m -vet=off
2025/10/08 10:02:46 Creating Terraform AWS Provider (SDKv2-style)...
2025/10/08 10:02:46 Initializing Terraform AWS Provider (SDKv2-style)...
--- PASS: TestAccVPCSecurityGroupIngressRule_Identity_RegionOverride (31.91s)
--- PASS: TestAccVPCSecurityGroupIngressRule_Identity_Basic (37.47s)
--- PASS: TestAccVPCSecurityGroupIngressRule_Identity_ExistingResource_NoRefresh_NoChange (52.26s)
--- PASS: TestAccVPCSecurityGroupIngressRule_Identity_ExistingResource (60.43s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/ec2 68.051s
Co-authored-by: Jared Baker <[email protected]>
Warning This Issue has been closed, meaning that any additional comments are much easier for the maintainers to miss. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
Rollback Plan
If a change needs to be reverted, we will publish an updated version of the library.
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
Description
Relations
Relates #44375
References
Output from Acceptance Testing